More Pages: Grady Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16


Very useful and informative book on the RUP
Excellent Book on RUP - A Must Have
A goal oriented guide to RUP

Excellent!You'll get a process framework, lots of metrics and examples, and alternative methods for establishing and maintaining a real software quality and process improvement program. In other words, this book delivers exactly what the title promises and more.
Remains one of the bestHighlights of this book include:
(1) The same story telling approach he successfully used in his first book. The conversational writing style and the logical sequence of the book makes it easy to read. Moreover, the real life examples add credibility and make the content practical instead of merely blue sky theory.
(2) A complete survey of assessment methods, such as the CMM, Software Productivity Research's Software Quality and Productivity Assessment, and Hewlett-Packard's internal QUality Maturity System. The latter two are especially interesting because they are, in essence, balanced scorecards.
(3) Business-oriented - the approach taken never strays from cost/benefit and ROI.
The parts I especially liked included the chapter on software failure analysis (a personal interest), key lessons from adopting best practices, and moving past reasons not to succeed. In fact, if you get nothing else from this book the last part will make this book a worthwhile investment because he shows how to deal with the six most common excuses for not pursuing process improvement (or any other initiative for that matter).
As in Grady's other books there is a wealth of metrics, data and examples. While this book is longer than his other books, it's still a manageable 314 pages and is highly readable. If you are involved with software process improvement initiatives this book should be on your short list.
practical examples that you can use with your organization

Excellent!!
50% of God's workforce set free by this book!Imagine the Greece, Sudan, Nigeria, and other 3rd world countries with this truth.
My wife has ministered for 33 years and she loves it also.


Great Book
wonderful piece of writing

A simple guide to JoyThe book mainly focuses on finding that Christ-Self (or whatever you prefer to call your higher self)in the present, NOW & HERE. Bringing this consciousness into all your life activities and interactions. Growing with a sense of Joy and love. Being aware of your judgements and how they might bring you down,feeling a deep sense of purpose by aligning with your deeper self and finding unconditional self acceptance.
The book doesn't veer too far away from these basic lessons, although the guidance is very subtle it's very powerful.
Although the writing has it's own unique style, to give you an idea of the perspective, it is along the lines of Ekhart Tolle's-The Power of Now. If you liked that, you will also enjoy Conversations with JC. I should also mention that it is similar to the work of the authors friend-Arnold Patent (The Journey&You Can Have It All). If you like her message I recommend Mr. Patent's books because they are extremely well rounded he covers many topics and living life with this state of consciousness in all aspects.
JC is the hotest guy out of all of NSYNC if you ask me

If you want an entertaining book, this is it!That's the way Deja Vu is --
Kerri-Leigh Grady is a terrific writer who writes a fast-paced book that will keep you in stitches. It's funny, touching, and hard to "put down."
I recommend it highly!
Deja Vu Was A Fantastic Journey Into the Past!

Wisdom for Preaching
A Must Read for all Preachers

an excellent tool for locating & dissecting great minds
The only source for truly useful quotations.

succession succeeds
Trees, Ghosts and History

A comprehensive, clear-eyed, and lyrical biographyTate considers Davis a man of high ideals and great personal honor. At the same time, though, he had a "peculiarly inflexible mind" ("he had not learned anything since about 1843") (p. 197) and a "feeble grasp of human nature" (p. 255). He treated his office as a sort of super-minister of defense, and was never "the leader of the Southern people as a whole" (p. 180). The South could have won the war if she had had the right kind of political leader, Tate argues. But Davis, whose rise to leadership was generally unearned (p. 79), wasn't it.
Beyond Davis the man, Tate also has a deep grasp of the Southern culture and the larger historical and cultural issues that were clashing in the War Between the States. In keeping with his Southern Agrarianism, Tate paints the South as the last outpost of European culture in the Americas, standing against -- and ultimately overwhelmed by -- the surging might of restless, expansionist, wealth-seeking "Americanism," embodied in the Yankee Northeast. Tate's grasp of Southern regionalism lets him place an emphasis on the tensions between Upper and Lower South that, for me, shone a light on the instability of the Confederate government that I haven't seen as emphasized elsewhere.
Tate's perspective and narrative form may not be in keeping with more modern styles of biography. But this book is nevertheless an excellent and insightful read, and I recommend it to any student of the men caught up in, as well as the issues behind, America's bloodiest conflict.
Eminently readable biographyThis is an absorbing read that puts one in mind of Shelby Foote's celebrated War trilogy, although Tate's was written first. It has the same novelistic quality and drive and the same quickly drawn but utterly convincing characterizations. The book alternates between presentations of certain monumental battles and portraits of life on the "homefront." The latter is actually more fascinating than the former. We learn in vivid detail of the strength and loyalty and perseverance of the Southern people.
- "The Rational Unified Process, An Introduction", by Philippe Kruchthen
- This book
- The Eeles et al. book on J2EE and RUP.
I haven't read any of the other two books, so I cannot tell you how this book falls into the greater scheme of things. I.e. I do not know what sort of overlap exists with the RUP Intro book, or which of the two to read first, etc. What I can tell you though is that this book, as it stands on its own, is a very good book in helping you (a) understand what the RUP is and (b) understand how to apply it on your projects.
First of all, the two authors of the book are as authoritative as can be. Kruchten (the author of the Intro book) is the chief technical RUP guy in Rational. Kroll is the Rational director (or whatever his new title is now under IBM) responsible for the RUP. These guys know the RUP and in a sense _are_ the RUP.
Now, to focus more on the book per se, it is as follows: It starts with a general intro chapter and then it moves on to chapter 2, which captures the so-called "Spirit of the RUP". It contains 8 tenets which sort-of summarize the philosophy of the RUP. Just as with a legal system, where it is not sufficient to only know articles of laws and statutes but you have to be extremely familiar and cognizant of the context in which these laws are applied and the purpose they serve in order to judge correctly, similarly with the RUP you don't only need to know the product with all the info and features it provides, but you need to have absorbed the philosophy that governs the process in order to apply the given material in the appropriate and most fruitful manner.
Chapter 3 I found (the emphasis is on "I"; you mileage may vary) the most useful. It basically charts the whole territory of processes that are out there (RUP, XP, other agile processes, heavyweight assessment standards such as the CMM) based on two important criteria, and tries to make you understand where RUP falls in the plane (and it is not really a fixed point, as RUP is customizable so there is some sort of leeway in how much iterative and/or ceremonial we want it to be).
Chapter 4 is an aberattion to the rest of the book IMHO, and I haven't found it much useful, or to my liking. It basically tries to explain RUP phases etc. in the context of a one-man project. I am not saying that this is necessarily a bad way to try to introduce people to the concepts of RUP in a more practical context - maybe you'll like it; I just didn't.
Afterwards, in chapter 5-9 we have an expounding of the 4 RUP phases, while chapter 10 is product-specific. Chapter 11 is extremely important as it talks about how to adopt the RUP in your organization, and proposes as the way to do so, treating the RUP adoption as a project of its own and applying some sort of "meta-RUP" on it; very interesting! Chapter 12 talks about planning an iterative project and Ch. 13 covers "antipatterns" (although the authors, to their credit, avoid using that term). Ch. 13 is very important reading and some of the stuff in there (e.g. the discussion on what constitutes a bad use case) you will find useful in a context much wider than the RUP.
Because each one of the roles (PM, Architect, Developer, etc.) views the process from their own unique perspective (just as power forward views the ballgame more in the perspective of getting many rebounds, whereas the point guard views in the sense of passing assists and shooting the occasional 3-pointer) it is very useful to have a chapter discussing each role's unique perspective of the RUP. My opinion is the all roles must read the chapters for all roles, but if you are short on time, this also helps you focus on the stuff strictly pertaining to your role. Although I am not a tester per se, I liked very much the discussion on "Good Enough Quality" in the Tester chapter. "Paradigms of Good Enough" and "The Cost of Quality" I have found to be a "must-read".
Also, the book has good references (both books and Web articles - especially from the RationalEdge) and the usual good quality you would expect from an AW publication in general and an OTS book in particular. Finally, even though in the intro the authors play a little pun on themselves on being French and Swedish respectively and thus non-native English speakers, don't get scared by that comment. Their English is excellent.
All in all, a very good and useful read. Buy it if only for chapters 3, 13, and 18. Actually, you may want to buy it even if you are not intending to use the RUP.